5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

When SET Destination is a Number


The numerical value of the source field, determined as described below, is copied to the destination field. No formatting is performed on the destination field, which is stored in the binary or packed form appropriate to the destination field's definition in the data dictionary. The source field value is rounded to the decimal positions of the destination field. If the destination field is not large enough to hold the integer part of the source field value, a numeric overflow condition results. Overflow processing is dependent on the use of OVERFLOW statements within the event point that contains the SET statement.

Source number

Number source fields are copied using conversion routines appropriate to the type and decimal positions of the source and destination fields. If the source field is null, the destination field is set to the destination field's null value.

Source alpha

The source field is tested for a valid numeric value. To be valid, the source field must contain only digits, an optional decimal point, an optional leading or trailing sign, and optional leading and/or trail-ing spaces. If the source field is blank, the destination field is set to the destination field's null value. If the source field does not contain a number, a non-recoverable error occurs.

Source date

The source field is converted to a packed decimal Gregorian date intermediate form, if necessary, before the copy operation. The integer packed decimal number representing the date is then copied to the destination field, ignoring the decimal positions of the destination field. For example, if the source field contains the value for January 1, 1988, and the destination field is defined with four digits to the left of the decimal point and two digits to the right of the decimal point, the destination field receives the value 880101.00.

Source logic

If the value of the source field is 1 (yes), the destination field is set to a value of 1. If the value of the source field is 0 (no), the destination field is set to a value of 0. If the value of the source field is blank, the destination field is set to null, according to the destination field's definition in the data dictionary.

Application Design Manual                                         "Powered by Appx Software"

693

©2006 By APPX Software, Inc. All Rights Reserved